docs: add raw deployment guide (Render + Vercel) - #48
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: yash-pouranik <172860064+yash-pouranik@users.noreply.github.com>
|
|
||
| - A [GitHub](https://github.com) account with a fork of this repository. | ||
| - A [MongoDB Atlas](https://www.mongodb.com/atlas) account (free). | ||
| - An [Upstash](https://upstash.com) account (free). |
There was a problem hiding this comment.
Done in af8edf7 — replaced Upstash with Redis Cloud (redis.io) throughout the prerequisites section, table, and further reading.
| - Username: `urbackend-user` | ||
| - Password: generate a strong password and **copy it**. | ||
| - Role: **"Read and write to any database"**. | ||
| 6. Under **Security → Network Access**, click **"Add IP Address"** → select **"Allow Access from Anywhere"** (`0.0.0.0/0`). |
There was a problem hiding this comment.
| 6. Under **Security → Network Access**, click **"Add IP Address"** → select **"Allow Access from Anywhere"** (`0.0.0.0/0`). | |
| 6. Under **Security → Network Access**, click **"Add IP Address"** → select **"add the IP(s) of your deployed instance in render"** (`0.0.0.0/0`). |
render exposes 2-6 of its unique ips of the proj you deploy, so dont say allow from anywhere ok? @copilot
There was a problem hiding this comment.
Updated in af8edf7. The step now reads:
Under Security → Network Access, click "Add IP Address" and add the outbound IP addresses of your Render service.
To find these IPs: open your Render service → Info tab → Outbound IPs. Render exposes a set of static outbound IPs per service; add each one individually in Atlas.
| - Role: **"Read and write to any database"**. | ||
| 6. Under **Security → Network Access**, click **"Add IP Address"** → select **"Allow Access from Anywhere"** (`0.0.0.0/0`). | ||
|
|
||
| > This is required because Render uses dynamic IP addresses. |
There was a problem hiding this comment.
Yes, removed in af8edf7. Since we're now directing users to add Render's specific outbound IPs, the "dynamic IPs" note is no longer accurate and has been deleted.
| ## 3. Set up Upstash Redis | ||
|
|
||
| 1. Go to [console.upstash.com](https://console.upstash.com) and sign in. | ||
| 2. Click **"Create Database"**. | ||
| 3. Enter a name (e.g. `urbackend-redis`), choose the region closest to your Render region, and leave the type as **Regional**. | ||
| 4. Click **"Create"**. | ||
| 5. On the database details page, scroll to **"REST API"** or **"Connect"** and copy the **Redis URL**. It looks like: | ||
|
|
There was a problem hiding this comment.
replace with redis.io setup
There was a problem hiding this comment.
Replaced in af8edf7. Section 3 now covers Redis Cloud at redis.io/try-free, including steps to create a free database and construct the rediss:// TLS connection URL.
| ## 📚 Further reading | ||
|
|
||
| - [MongoDB Atlas documentation](https://www.mongodb.com/docs/atlas/) | ||
| - [Upstash Redis documentation](https://upstash.com/docs/redis/overall/getstarted) |
There was a problem hiding this comment.
Updated in af8edf7 — further reading now links to the Redis Cloud documentation at redis.io/docs/latest/operate/rc/.
Co-authored-by: yash-pouranik <172860064+yash-pouranik@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds self-hosting documentation so developers can deploy urBackend without Docker, targeting a free-tier setup with Render (backend) and Vercel (frontend).
Changes:
- Added a new
DEPLOYMENT.mdwith end-to-end deployment steps (MongoDB Atlas + Redis Cloud + Render + Vercel) and troubleshooting. - Linked the new deployment guide from
README.mdunder a “Self-Hosting” section.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| README.md | Adds a Self-Hosting section linking to the deployment guide. |
| DEPLOYMENT.md | Introduces a platform-specific deployment guide for Render (API) + Vercel (dashboard), including env vars and troubleshooting. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
No self-hosting documentation existed for deploying urBackend outside of Docker. This adds a complete, platform-specific deployment guide targeting free-tier Render (backend) and Vercel (frontend).
DEPLOYMENT.md(new)backend,npm install/npm start, full env-var reference derived from.env.exampleincluding secrets generation tip:node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"rediss://connection URLfrontend, Vite auto-detection,VITE_API_URLpointing to the Render service URLFRONTEND_URLon Render after the Vercel URL is known to unblock CORSREADME.mdDEPLOYMENT.mdOriginal prompt
💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.